Backend architecture.

The full flow.

All 8 diagnostics (WIA, PBR, ICR, TSR, EPR, ExR, FOR, MAR) are currently client-side prototypes using localStorage for state persistence. Production requires server-side submission, storage, PDF generation, and email delivery — plus admin views for Chekelah's team.

The data model.

Table: submissions

Master table for every diagnostic submission across all 8 report types.

CREATE TABLE submissions (
  id              TEXT PRIMARY KEY,           -- UUID v7
  diagnostic      TEXT NOT NULL,             -- WIA | PBR | ICR | TSR | EPR | ExR | FOR | MAR | BOD
  version         TEXT NOT NULL,             -- v1
  submitted_at    INTEGER NOT NULL,          -- unix ms
  applicant_name  TEXT,
  applicant_email TEXT NOT NULL,
  applicant_phone TEXT,
  applicant_company TEXT,
  consent_terms   INTEGER NOT NULL,          -- 1 = accepted
  raw_state       TEXT NOT NULL,             -- JSON of all form answers
  ip_hash         TEXT,                      -- SHA-256 (privacy-preserving)
  user_agent      TEXT,
  turnstile_score REAL,
  utm_source      TEXT,
  utm_campaign    TEXT,
  status          TEXT NOT NULL DEFAULT 'submitted'  -- submitted | pdf-generated | delivered | reviewed | routed
);

CREATE INDEX idx_sub_email ON submissions(applicant_email);
CREATE INDEX idx_sub_diagnostic ON submissions(diagnostic, submitted_at DESC);
CREATE INDEX idx_sub_status ON submissions(status);

Table: scores

Computed scores for each submission — derived from raw_state at submission time, cached for admin queries.

CREATE TABLE scores (
  submission_id   TEXT PRIMARY KEY REFERENCES submissions(id),
  overall_score   INTEGER NOT NULL,          -- 0-100
  tier_band       TEXT NOT NULL,             -- e.g. "TIER 03 · COORDINATION-READY"
  tier_verdict    TEXT NOT NULL,
  top_moves       TEXT NOT NULL,             -- JSON array of 6-12 moves with per-move scores
  computed_at     INTEGER NOT NULL
);

Table: routing

Specialist-routing recommendations produced by the diagnostic — used to trigger partner-firm handoffs.

CREATE TABLE routing (
  id              TEXT PRIMARY KEY,
  submission_id   TEXT NOT NULL REFERENCES submissions(id),
  specialist_type TEXT NOT NULL,             -- CPA | ATTORNEY | LENDER | IB | INSURANCE | RIA
  discipline      TEXT NOT NULL,             -- ESTATE, M&A, TAX-PLANNING, SBA, JUMBO, etc.
  urgency         TEXT NOT NULL,             -- URGENT | HIGH | STANDARD
  partner_id      TEXT REFERENCES partners(id), -- nullable · matched later
  status          TEXT NOT NULL DEFAULT 'unmatched', -- unmatched | matched | intro-sent | engaged | closed
  created_at      INTEGER NOT NULL
);

Table: partners

Vetted partner firms (from Partnership Program) — matched to routing entries.

CREATE TABLE partners (
  id              TEXT PRIMARY KEY,
  firm_name       TEXT NOT NULL,
  primary_contact TEXT NOT NULL,
  email           TEXT NOT NULL,
  specialist_type TEXT NOT NULL,
  disciplines     TEXT NOT NULL,             -- JSON array
  geography       TEXT NOT NULL,             -- e.g. "DFW", "NATIONAL"
  mou_signed_at   INTEGER,
  status          TEXT NOT NULL DEFAULT 'active' -- active | paused | ended
);

Table: reports

Generated PDF reports — R2 object references.

CREATE TABLE reports (
  submission_id   TEXT PRIMARY KEY REFERENCES submissions(id),
  r2_key          TEXT NOT NULL,             -- "reports/{id}.pdf"
  pdf_size_bytes  INTEGER NOT NULL,
  generated_at    INTEGER NOT NULL,
  delivered_at    INTEGER,
  version         TEXT NOT NULL              -- template version
);

The endpoints.

POST /api/submit

Accepts a diagnostic form submission from the client. Validates, stores, scores, and queues downstream jobs.

// Request body
{
  "diagnostic": "WIA" | "PBR" | "ICR" | "TSR" | "EPR" | "ExR" | "FOR" | "MAR" | "BOD",
  "version": "v1",
  "applicant": {
    "name": "...",
    "email": "...",
    "phone": "...",
    "company": "..."
  },
  "state": { /* full form state, as stored in localStorage */ },
  "turnstile": "...",             // Cloudflare Turnstile CAPTCHA token
  "consent": true
}

// Response
{
  "ok": true,
  "submission_id": "uuid-v7",
  "score": 74,
  "tier_band": "TIER 03 · COORDINATION-READY",
  "report_eta": "2025-11-15T10:00:00Z"
}

GET /admin/queue

Admin-authenticated endpoint (Cloudflare Access-gated) for Chekelah's team to review incoming submissions.

{
  "total_pending_review": 12,
  "submissions": [
    {
      "id": "...",
      "diagnostic": "ICR",
      "applicant": { "name": "...", "email": "...", "company": "..." },
      "score": 74,
      "tier_band": "...",
      "submitted_at": 1730000000000,
      "pdf_url": "https://reports.hlpcredit.com/...",
      "routing_recommendations": [ /* array of specialist recs */ ]
    }
  ]
}

POST /admin/route/:submission_id

Chekelah's team matches routing entries to specific partner firms + sends warm-intro emails.

The Report™ generator.

PDF generation runs as a queued job — decoupled from the submit response to keep the client-side experience snappy.

Pipeline

Templates

Every diagnostic has its own PDF template stored in R2. Templates use Handlebars for dynamic score data + move rendering:

templates/
├── WIA/v1/
│   ├── template.html          // Handlebars HTML
│   ├── styles.css             // Print-optimized CSS
│   └── cover.svg
├── PBR/v1/
├── ICR/v1/
├── TSR/v1/
├── EPR/v1/
├── ExR/v1/
├── FOR/v1/
├── MAR/v1/
└── shared/
    ├── header.html            // HLP logo + report meta
    ├── footer.html            // Compliance disclaimer
    └── styles-base.css

The 48-hour promise.

Every diagnostic promises delivery within 48 hours. Two-stage email flow ensures both machine-speed acknowledgment and human-review completion.

Email is sent via Cloudflare Email Routing for inbound and Resend for outbound transactional. MJML templates render to responsive HTML.

The guardrails.

Where it lives.

Following the existing HLP subdomain architecture:

The build order.

Recommended 4-phase implementation:

1. Phase 1 · Week 1-2: D1 schema · Worker /api/submit · basic PDF generation (single template) · admin queue view
2. Phase 2 · Week 3-4: All 8 report PDF templates · email delivery pipeline · signed URLs · Turnstile CAPTCHA
3. Phase 3 · Week 5-6: Admin routing UI · partner-matching workflow · warm-intro email automation
4. Phase 4 · Week 7-8: Analytics dashboard · GLBA/CCPA export endpoints · retention automation · MFA hardening